Watch list jamming would be extremely cool to have. As it stands, nonconsensual watch listing provides way too much intelligence about enemy forces in a way that is extremely easy to read from the client's memory and output into an irc channel. Short of removing nonconsensual watchlisting, having a mechanism to blunt its effectiveness would be marvelous.

I really like the open discussions and concepts exposed in the structure presentation. I think CCP is doing a great job of putting theses on the table and have us comment on them upfront.

As for this specific topic about observatory arrays, the most important thing is to make sure these structures help active connected pilots, and put a significant risk on inactive pilots not in a safe zone (POS or Station).

I fully support the concept of a system wide de-cloaking pulse from an observatory array, as long as it can only be activated by a pilot that has to go to the observatory array, and trigger the pulse there from a module that would "sync" with the structure (much like the upcoming entosis link, so not doing it from a pod, not doing it remotely from a safe spot, or worse without even being in the system). The module could have variations, selected by the pilot, to bring some kind of effect variation to such a pulse (delay, strength, range,.. whatever..)

I think these structures should not necessarily be inside a POS shield but placed around the system, larger systems requiring possibly more of such structures.
They would still need to link to an online POS somehow (or was there any mention that these new structures will be deployed independently of POSes?).

Overall, I do not recommend having various roles for the same structure. A gate is used to go from System A to System B. If something should affect the warp speed in a system, that should be a new structure on its own. Deployable structures like that should stick to one role only, as multiplying effect on the same structure will lead to higher risks of unbalance.

I think people like afkalt are looking at this from the wrong point of view.

Null needs to be safe to attract the people that make the space worth living (or worth roaming to), at least to some degree. If miners and industrialists don't want to come to null because it's not safe enough for them, it's going to remain as desolate as it is. That's bad.

On the other hand, I've had the problem on multiple occasions that random gank fleets, 5 ppl or less are just uncatchable by 50 ppl +, just by bouncing safe spots and waiting out the safe log off timer.

It's also very, very wrong that the owning side can't force a fight eventually.

I'm ok with gankers blitzing a constellation and killing one or two people, but them being able to bounce for hours on end if they want to is plain OP. Same as cloaky campers.

The Observation Arrays are a part of the solution to that.

The Decloaking should be manual and with a timer, it could even provide a proximity warning like the ESS.

The Observation Arrays COULD also provide warp end point bookmarks or anomaly beacons to the owning party for where said raiding party ends warps after bouncing. After a certain "lock" time if you will.

So like a raider has been in a system for 30 minutes, received 3 warnings that the lock on him is getting more accurate, after that when he warps the OA calculates the end point and creates an anomaly. Interceptors can warp to that and try to catch him and fight.

Also Right now you can limit wh spawns(I hub upgrades?), and how limiting warp speed is making a SOV owners paradise? Remeber that warping time is the isk when you run anomalies, so every ratting system will rather boost the warp speed : )

Also This "Advanced intel" will not help against Combat probers with interceptors ^^ i have no idea how deleyed local can prevent carebers from beeing tackled.